@0x29a, the change looks good to me, but I need to check something first, so I'll review this next week.

We cannot use the opencraft-release/palm.1 for this client because it uses @edx/frontend-platform v2.5.0, incompatible with a custom header component in Palm. Therefore, I created the opencraft-release/palm.1-echo branch for them, which includes ae1702d (that bumps @edx/frontend-platform version from 2.5.0 to ^4.2.0). Our opencraft-release/palm.1 does not have these changes, but it contains the cherry-picked 3644172. Therefore, I created opencraft-release/palm.1-echo-2, which includes all commits up to 3be81e0. I'll be deploying it to the client instance to test it. Then, I'd like to rebase our opencraft-release/palm.1 branch onto it.

Could it cause any trouble for the other client that uses this repo?

Could it cause any trouble for the other client that uses this repo?

@Agrendalath, I'm not that involved in the frontend development for this client, but I don't think it has any customizations that would conflict with the changes you're going to add.

@navinkarkera, do you know if bumping @edx/frontend-platform version from 2.5.0 to ^4.2.0 (ae1702d) in the gradebook MFE can break something for ASU?

@0x29a Unfortunately, I don't know.

cc: @viadanna, as the client owner ^

I don't see a problem 👍

I replaced the branches as described above. The original opencraft-release/palm.1 is now opencraft-release/palm.1-asu-backup.